Post

Replies

Boosts

Views

Activity

Reply to Failed to load embed dylib in M1?
I used otool -l to get some information on my lib. Does anybody know why the load path will be different within the same project? For Intel: Load command 11           cmd LC_LOAD_DYLIB       cmdsize 56          name @rpath/libavcodec.58.dylib (offset 24)    time stamp 2 Thu Jan  1 08:00:02 1970       current version 58.54.100 compatibility version 58.0.0 For Arm Load command 12           cmd LC_LOAD_DYLIB       cmdsize 64          name /usr/local/lib/libavcodec.58.dylib (offset 24)    time stamp 2 Thu Jan  1 08:00:02 1970       current version 58.54.100 compatibility version 58.0.0
Dec ’21
Reply to Failed to load embed dylib in M1?
For additional reference, I was building the ffmpeg library for Arm. The Intel part I got from my previous owner directly. I just using the same build config got from the original owner to build the Arm build and using lipo to combine these two library into one to be used in my app. I am wondering are there something I am missing when I build the Arm version. Are there any possible hint to find the solution?
Dec ’21
Reply to Failed to load embed dylib in M1?
I used otool -l to get some information on my lib. Does anybody know why the load path will be different within the same project? For Intel: Load command 11           cmd LC_LOAD_DYLIB       cmdsize 56          name @rpath/libavcodec.58.dylib (offset 24)    time stamp 2 Thu Jan  1 08:00:02 1970       current version 58.54.100 compatibility version 58.0.0 For Arm Load command 12           cmd LC_LOAD_DYLIB       cmdsize 64          name /usr/local/lib/libavcodec.58.dylib (offset 24)    time stamp 2 Thu Jan  1 08:00:02 1970       current version 58.54.100 compatibility version 58.0.0
Replies
Boosts
Views
Activity
Dec ’21
Reply to Failed to load embed dylib in M1?
For additional reference, I was building the ffmpeg library for Arm. The Intel part I got from my previous owner directly. I just using the same build config got from the original owner to build the Arm build and using lipo to combine these two library into one to be used in my app. I am wondering are there something I am missing when I build the Arm version. Are there any possible hint to find the solution?
Replies
Boosts
Views
Activity
Dec ’21
Reply to My app is damaged and can't be opened when porting to M1 ?
Thanks, got it.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Dec ’21
Reply to Failed to recognize core graphic after update Xcode 13.1?
At last I add additional import in my .mm file to fix this issue. But I don't know why I don't need to do this before Xcode update.
Replies
Boosts
Views
Activity
Dec ’21
Reply to Failed to recognize core graphic after update Xcode 13.1?
Still got the same problem now -_-.....
Replies
Boosts
Views
Activity
Nov ’21
Reply to My app is damaged and can't be opened when porting to M1 ?
I found the solution. I can just using xattr -c on my app. Then this issue gone.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’21
Reply to How can I combine two different dylib into a simple one?
I have done this by lipo command such as lipo -create ./dylib_intel/libavcodec.58.dylib ./dylib_arm/libavcodec.58.dylib -output ./dylib_universal/libavcodec.58.dylib
Replies
Boosts
Views
Activity
Oct ’21